Skip to main content

Cloud Credential Profile in ObserveOps

Use the Cloud protocol to monitor cloud infrastructure. Select the tab that matches your provider. Each cloud provider has its own set of required credentials.

AWS

Cloud credential form with AWS tab selected showing Access Key and Secret Key fields

FieldDescription
Access KeyThe AWS IAM access key ID that identifies the IAM user or role ObserveOps uses to query your AWS account.
Secret KeyThe AWS IAM secret access key paired with the access key above.

Azure

Cloud credential form with Azure tab selected showing Client ID, Tenant ID, and Secret Key fields

FieldDescription
Client IDThe Application (client) ID of your Azure app registration that ObserveOps uses to authenticate.
Tenant IDThe Directory (tenant) ID of your Azure Active Directory where the app registration lives.
Secret KeyThe client secret generated for the app registration above.

Office 365

Cloud credential form with Office 365 tab selected showing Client ID, Tenant ID, and Secret Key fields

FieldDescription
Client IDThe Application (client) ID from your Microsoft Entra app registration for this ObserveOps integration.
Tenant IDThe Directory (tenant) ID of your Microsoft 365 tenant.
Secret KeyThe client secret for the app registration above.

Oracle Cloud

Cloud credential form with Oracle Cloud tab selected showing Tenancy OCID, User OCID, Private Key, and Fingerprint fields

FieldDescription
Tenancy OCIDThe Oracle Cloud Identifier for your tenancy, found in the Oracle Cloud Console under Tenancy Details.
User OCIDThe OCID of the user whose API signing key ObserveOps uses for authentication.
Private KeyThe PEM private key from the API signing key pair uploaded to your Oracle Cloud user profile.
FingerprintThe fingerprint of the public key uploaded to your Oracle Cloud user profile, used to verify the signing key.

Google Cloud

Cloud credential form with Google Cloud tab selected showing Client ID, Client Secret, Auth URL, Token URL, Redirect URL, Timeout, and Scope fields

FieldDescription
Client IDThe OAuth 2.0 client ID from your Google Cloud project that ObserveOps uses for authentication.
Client SecretThe OAuth 2.0 client secret paired with the client ID above.
Authentication URLThe Google OAuth authorization endpoint URL where ObserveOps requests authorization.
Token URLThe Google OAuth token exchange endpoint URL where ObserveOps exchanges authorization codes for access tokens.
Redirect URLThe redirect URI registered in your Google Cloud OAuth configuration. Leave empty if not required by your setup.
Timeout (sec)The number of seconds ObserveOps waits for a response before treating the connection as failed.
ScopeThe API scopes ObserveOps needs to access your Google Cloud resources, for example https://www.googleapis.com/auth/cloud-platform.